SOAP formats supported by Progress 4GL Web services
Most Web service message formats pair Document style with Literal use and pair RPC style with Encoded use. However, Progress 4GL Web services support three SOAP message formats, with the features shown in Table 2–2.
Table 2–2: Supported SOAP message formats
|
SOAP format
|
Progress 4GL Web services features
|
|
RPC/Encoded
|
The client interface object method normally has the same function signature as the 4GL procedure/function. This is possible because the WSDL for RPC/encoded includes a parameterOrder attribute on each request/response pair (operation). A return value (result) is always present in the response message for a user-defined function. A return value (result) is present in the response message for a procedure only if specified in ProxyGen (mapped to the 4GL RETURN-VALUE).
|
|
RPC/Literal
|
The features are identical to RPC/Encoded.
|
|
Document/Literal
|
The client interface object method might not have the same function signature as the 4GL procedure/function. This is because the WSDL for Document/Literal does not support the parameterOrder attribute. The client toolkits generally create a method signature with the parameters of the request message followed by the parameters of the response message. A return value (result) is always present in the response message for both procedures (mapped to the 4GL RETURN-VALUE) and user-defined functions. The client interface can represent this return value as a return value on the method or as an output parameter named "result", depending on the client platform.
|